Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Progress Explorer framework architecture

Figure 10–1 depicts the main elements of the Progress Explorer framework. It is intended to provide a conceptual understanding of the relationship that exists among these elements described in Table 10–1. (Additional comments about the diagram are presented after Figure 10–1.)

Figure 10–1: Overview of the Progress Explorer Framework

In addition to the footnotes associated with Table 10–1, note these points about Figure 10–1:

The AdminServer, through its default port 20931 as shown in the diagram, processes start, stop, and query requests initiated from a requesting OpenEdge product. Similarly, the database, NameServer, AppServer, and WebSpeed brokers have their own default ports.

As part of setting up and maintaining security measures for your machines, it is advisable to change default port numbers and server names. These actions help to protect their identifies from personnel outside your organization. Also, consider documenting and monitoring all of your ports (that is, the port numbers and types) that you use for the AdminServer.

The dotted lines connecting the ubroker.properties file and conmgr.properties file to their respective OpenEdge products is intended to indicate that the commands entered and accepted either through the Progress Explorer tool or the mergeprop utility directly affect the data stored in the ubroker.properties file or conmrg.properties file.
Because your ubroker.properties and conmgr.properties files contain the detailed configuration data for each OpenEdge product, ensure that you backup these files periodically.
Similarly, from a security perspective, it is good practice change the default ports noted in Figure 10–1 and document the new port numbers you use instead.